Transacting in advance

ABSTRACT

Various embodiments generally relate to generating and scheduling transactions in advance. More specifically, various embodiments relate to receiving a request for a transaction from a user device; processing the transaction, where the transaction requires some user interaction at a point of transaction to complete the transaction; identifying a location for completion of the transaction; determining possible points of transaction within a predetermined distance of the identified location; displaying the possible points of transaction; receiving a selection of one of the possible points of transaction; generating a unique identifier for the transaction based on the selected point of transaction; and sending the unique identifier for presentation at the selected point of transaction, where the unique identifier is used to complete the transaction.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/460,881, filed Jul. 2, 2019, now allowed, which is a continuation ofU.S. patent Ser. No. 13/673,663, filed Nov. 9, 2012, entitled“TRANSACTING IN ADVANCE,” issued as U.S. Pat. No. 10,387,876 on Aug. 20,2019; which claims priority to U.S. Provisional Application No.61/557,636, filed on Nov. 9, 2011, entitled “Banking In Advance” whichis hereby incorporated by reference for all purposes in its entirety.This disclosure is also related to U.S. Provisional Application No.61/881,920 entitled “PROACTIVE BANK TRANSACTION STAGING PROCESS FORSMART DEVICES,” filed on Sep. 24, 2013 and U.S. patent application Ser.No. 14/201,736, filed on Mar. 7, 2014, entitled “PROACTIVE BANKTRANSACTION STAGING METHODS AND SYSTEMS,” issued as U.S. Pat. No.10,373,148 on Aug. 6, 2019.

TECHNICAL FIELD

Various embodiments of the present invention generally relate totransactions. More specifically, methods and systems for generating andstaging transactions at a point of transaction are disclosed.

BACKGROUND

Accomplishing financial transactions at banking locations such as ATMs,kiosks, and brick-and-mortar banks can sometimes impose significant waittimes for customers. Whether a customer is waiting in line at an ATM, ata customer service counter for their transaction to be processed, orbehind many cars in a drive-up teller lane at a bank, the time lostwaiting can frustrate customers.

Therefore, customers may prefer to accomplish transactions, or at leastas much of the transaction as possible, outside of banking locations andcomplete the transaction quickly at a scheduled time at a convenientbanking location.

SUMMARY

One embodiment includes a method that includes receiving a request for atransaction from a user device of a user, where completion of thetransaction requires user interaction at a point of transaction;identifying a location for completion of the transaction; determiningpossible points of transaction within a predetermined distance of theidentified location; displaying the possible points of transaction;receiving a selection of one of the possible points of transaction;generating a unique identifier for the transaction based on the selectedpoint of transaction; and sending, to the user, the unique identifierfor presentation at the selected point of transaction, where the uniqueidentifier is used to complete the transaction.

In some embodiments, generating the unique identifier includespopulating the unique identifier with information relating to thetransaction. In some embodiments, a content of the information relatingto the transaction is based at least in part on a relationship with theselected point of transaction. In some embodiments, a content of theinformation relating to the transaction is based at least in part oncapability of the selected point of transaction. In some embodiments,information relating to the transaction includes an account number, atype of transaction, and a transaction identifier. In some embodiments,the unique identifier is a transaction identifier. In some embodiments,the unique identifier includes a machine-readable identifier. Themachine readable identifier may be selected from the group including aquick response code and a universal product code.

In some embodiments, the point of transaction is associated with anaffiliated organization, where information relating to the transactionis accessed by the point of transaction using the unique identifier.

The method may further include receiving the unique identifier;accessing user records to identify the transaction; and communicatinginformation relating to the transaction to the point of transactionsufficient to complete the transaction at the point of transaction.Identifying a location for completion of the transaction may includedetecting a location of the user device.

The method may further include authenticating the user at the point oftransaction using the unique identifier in combination with the userdevice.

In some embodiments, generating the unique identifier comprisesassigning an expiration time to the unique identifier.

In some embodiments, the method further includes detecting that the useris within a radius of the point of transaction; scheduling thetransaction for completion at the point of transaction; andcommunicating to the user that the transaction is ready for completion.

In some embodiments, the method further includes detecting that the useris within a radius of one of the possible points of transaction that isnot the selected point of transaction; and communicating to the userthat the transaction can be completed at the possible point oftransaction. The method may further include receiving an indication thatthe user will complete the transaction at the possible point oftransaction that is not the selected point of transaction; generating asecond unique identifier for the transaction based on characteristics ofthe possible point of transaction that is not the selected point oftransaction; and sending the second unique identifier to the user.

In some embodiments, the method further includes registering the userdevice with a customer account, and registering the user device with acustomer account includes receiving a request to register the userdevice with the customer account; collecting identifying informationrelated to the user device; and associating the user device and theidentifying information related to the user device with the customeraccount.

In some embodiments, the point of transaction is a physical location,and displaying the possible points of transaction includes indicatingthe possible point of transaction on a map.

One embodiment includes a non-transitory machine-readable medium havingmachine executable instructions stored thereon that, when executed byone or more processors, direct the one or more processors to perform amethod including receiving a request for a transaction from a userdevice of a user, where completion of the transaction requires userinteraction at a point of transaction; identifying a location forcompletion of the transaction, where identifying the location forcompletion of the transaction comprises detecting a location of the userdevice; determining possible points of transaction within apredetermined distance of the identified location; displaying thepossible points of transaction; receiving a selection of one of thepossible points of transaction; generating a unique identifier for thetransaction based on the selected point of transaction, where generatingthe unique identifier includes populating the unique identifier withinformation relating to the transaction, and assigning an expirationtime to the unique identifier, where information relating to thetransaction includes an account number, a type of transaction, and atransaction identifier, where the unique identifier comprises amachine-readable identifier, where a content of the information relatingto the transaction is based at least in part on a relationship with theselected point of transaction; sending, to the user, the uniqueidentifier for presentation at the selected point of transaction, wherethe unique identifier is used to complete the transaction; receiving theunique identifier from the selected point of transaction; accessing userrecords to identify the transaction; communicating information relatingto the transaction to the point of transaction sufficient to completethe transaction at the point of transaction; and completing thetransaction.

In one embodiment, a system includes one or more processors; andcomputer-readable code that programs the one or more processors toreceive a request for a transaction from a user device of a user, wherecompletion of the transaction requires user interaction at a point oftransaction; identify a location for completion of the transaction,where identifying the location for completion of the transactioncomprises detecting a location of the user device; determine possiblepoints of transaction within a predetermined distance of the identifiedlocation; display the possible points of transaction; receive aselection of one of the possible points of transaction; generate aunique identifier for the transaction based on the selected point oftransaction, where generating the unique identifier includes populatingthe unique identifier with information relating to the transaction, andassigning an expiration time to the unique identifier, where informationrelating to the transaction comprises an account number, a type oftransaction, and a transaction identifier, where the unique identifiercomprises a machine-readable identifier, where a content of theinformation relating to the transaction is based at least in part on arelationship with the selected point of transaction; send, to the user,the unique identifier for presentation at the selected point oftransaction, where the unique identifier is used to complete thetransaction; receive the unique identifier from the selected point oftransaction; access user records to identify the transaction;communicate information relating to the transaction to the point oftransaction sufficient to complete the transaction at the point oftransaction; and complete the transaction.

While multiple embodiments are disclosed, still other embodiments of thepresent invention will become apparent to those skilled in the art fromthe following detailed description, which shows and describesillustrative embodiments of the invention. As will be realized, theinvention is capable of modifications in various aspects, all withoutdeparting from the scope of the present invention. Accordingly, thedrawings and detailed description are to be regarded as illustrative innature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will be described and explainedthrough the use of the accompanying drawings in which:

FIG. 1 illustrates an example of an operating environment in which someembodiments of the present invention may be utilized;

FIG. 2 is a block diagram illustrating components that can be includedin a system in accordance with various embodiments of the presentinvention;

FIG. 3 is a flow chart illustrating a set of operations in accordancewith some embodiments of the present invention;

FIG. 4 is a flow chart illustrating a set of operations in accordancewith some embodiments of the present invention;

FIG. 5 is a flow chart illustrating a set of operations in accordancewith some embodiments of the present invention;

FIG. 6 illustrates an example of a user interface;

FIG. 7 illustrates examples of user interfaces;

FIG. 8 illustrates an example of a user interface;

FIG. 9 illustrates an example of a user interface;

FIG. 10 illustrates examples of user interfaces;

FIG. 11 illustrates examples of user interfaces;

FIG. 12 illustrates an example of a user interface;

FIG. 13 illustrates examples of user interfaces;

FIG. 14 illustrates an example of a user interface;

FIG. 15 illustrates an example of a user interface;

FIG. 16 illustrates an example of a user interface;

FIG. 17 illustrates an example of a user interface;

FIG. 18 illustrates an example of a user interface;

FIG. 19 illustrates an example of a user interface;

FIG. 20 illustrates an example of a user interface;

FIG. 21 illustrates an example of a user interface; and

FIG. 22 illustrates an example of a computer system with which someembodiments of the present invention may be utilized.

The drawings have not necessarily been drawn to scale. For example, thedimensions of some of the elements in the figures may be expanded orreduced to help improve the understanding of the embodiments of thepresent invention. Similarly, some components and/or operations may beseparated into different blocks or operations or combined into a singleblock or operation for the purposes of discussion of some of theembodiments of the present invention. Moreover, while the invention isamenable to various modifications and alternative forms, specificembodiments have been shown by way of example in the drawings and aredescribed in detail below. The intention, however, is not to limit theinvention to the particular embodiments described. On the contrary, theinvention is intended to cover all modifications, equivalents, andalternatives falling within the scope of the invention as defined by theappended claims.

DETAILED DESCRIPTION

Various embodiments of the present invention generally relate totransactions. More specifically, methods and systems for generating andstaging transactions at a point of transaction are disclosed. In someembodiments, the transaction is a financial transaction. In someembodiments, a customer initiates and completes a portion of atransaction using a registered device, receives recommendations ofpoints of transactions where the transaction can be completed, andschedules a time to complete the transaction (or places the transactionin a queue) at the selected point of transaction. Therefore, at least aportion of the transaction may be completed prior to the time thecustomer goes to the point of transaction, and wait lines may be avoidedby scheduling a completion time of the transaction at the selected pointof transaction. Further, customers may prefer to complete a transactionto the extent possible in the privacy of their home or vehicle tominimize the risk of identity theft that has been problematic at ATMsand other banking locations.

In some embodiments, a customer requests a transaction that requiressome type of user interaction at a point of transaction to complete thetransaction, such as depositing cash, cashing a check, or providing asigned copy of a document. The user may identify where the customerwould like to complete the transaction. Sometimes, the customeridentifies a general location for completion or the user's mobile devicemay help determine a location. Points of transaction around the area ofthe identified completion location are determined. This determinationmay include an analysis of suitable and preferable points oftransaction. These possible points of transaction are displayed for thecustomer on the user device. The customer may select the particularpoint of transaction. A unique identifier may be generated for thetransaction and sent to the user. The customer may present the uniqueidentifier to the point of transaction, which identifies the transactionand, in some cases, authenticates the customer. The content of theinformation contained in the unique identifier may depend on thesophistication of the point of transaction and/or a relationship, ifany, with the transacting entity or financial institution. Commonlyassigned application U.S. patent application Ser. No. 13/425,227entitled “Dynamic Risk Engine” discusses performing activities on onechannel and transferring the activities seamlessly to a differentchannel during a session, which is hereby incorporated by reference forall purposes in its entirety.

In a specific example, a customer launches a mobile application, isauthenticated, selects the type of transaction such as “Deposit at aRetail Location,” (or the like) and selects an account to deposit into,along with the amount of the deposit, if known. The customer may simplyidentify the retail location or other point of transaction where theuser wishes to make the deposit, such as a CVS store, or a UPS store,etc. The transaction may be scheduled for completion at the selectedretail location. A unique identifier may be generated and sent to thecustomer to provide the point of transaction. The customer may presentthe unique identifier and make the deposit at the selected point oftransaction.

The description discusses financial transactions and “bankinglocations.” However, the references to financial transactions andbanking locations are for illustration only; the concepts are equallyapplicable to other types of transactions and various types of networkand physical locations.

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of embodiments of the present invention. It will beapparent, however, to one skilled in the art that embodiments of thepresent invention may be practiced without some of these specificdetails. For example, many of the embodiments are discussed with regardto examples involving banking transactions. One of skill in the art willrecognize that embodiments of the present invention are equallyapplicable to other types of transactions in other industries.

FIG. 1 illustrates an example of an operating environment 100 in whichsome embodiments of the present invention may be utilized. Theembodiments of the present invention illustrated in FIG. 1 allow userinteractions through various points of interaction such as, but notlimited to, dedicated terminals 110 (e.g., public terminal or kiosk),ATM networks 115 (e.g., interbank ATM network and intrabank ATMnetworks), mobile devices 120 (e.g., mobile phone, smartphone, laptop,tablet computer), personal computers 125, point of sale (POS) devices130, and vehicle 135. These points of interaction can include mechanismsfor generating, submitting and processing transactions through network140 to banking network 145 and may run one or more applications orclients that allow a user to interact with the banking network 145. Suchapplications may provide access to various banking processing systemsand interfaces that include banking functionality such as withdrawals,balance inquiries, deposits, transfers, etc.

Dedicated terminals 110 such as public terminals/kiosks may be computersavailable to the public and/or specially designed kiosks that interactwith banking network 145. ATM network 115 can be any set of ATMs in aninterbank ATM network and/or intrabank ATM network. Mobile device 120may be cellular phones, smart phones (a smart phone being a cellularphone that has capabilities and features such as, but not limited to,internet access, a full keyboard, email access, Wi-Fi connectioncapabilities, BLUETOOTH connectivity, or any other functionality of acomputer), tablet computers (a portable computer having a touchinterface), netbooks, and laptops possibly with a wireless connection(such as an 802.11a/b/g connection or mobile broadband connection, suchas via a 3G or 4G wireless network). Personal computer 125 may be anycomputer (e.g., desktop computers, laptop computers, netbooks, tabletcomputers, Internet-enabled television devices, etc.) connected tonetwork 140. Vehicle 135 may include software and/or hardware providinga system capable of communicating with the points of interaction.Additionally, a mobile device 120 or other device may be communicablycoupled with vehicle 135, such as via Bluetooth or other appropriatewireless link, hardwire connected to the vehicle 135, docked in aspecially-designed docking station integral to the vehicle 135 asdescribed in U.S. Provisional Application No. 61/481,036 “DedicatedShort-Range Communications (DSRC) to Make Payments from Vehicles UsingVehicle-Based, Cloud-Based or Smartphone-Based Mobile Wallets” and U.S.patent application Ser. No. 13/460,380 entitled “Dedicated Short-RangeCommunications (DSRC) to Make Payments from Vehicles UsingVehicle-Based, Cloud-Based or Smartphone-Based Mobile Wallets,” both ofwhich are hereby incorporated by reference in their entirety.

POS device 130 can be any device used as a checkout or payment receivingmechanism for a merchant or service provider such as a hospital,ambulance company, doctor, automobile repair shop, pharmacy, clothingstore, and others. For example, POS device 130 can be a terminal locatedat a merchant, a computer-based interface such as a webpage or customapplication, a telephone payment system, and others.

Banking network 145 may include any number of membership organizations,banks, credit unions, or other financial institutions. In accordancewith embodiments of the present disclosure, banking network 145 can usea variety of interaction methods, protocols, and systems. For example,banking network 145 can use any of the automated clearing house (ACH)networks. An ACH network may be operated by NACHA (previously referredto as the National Automated Clearing House Association). Another ACHnetwork may be the Electronic Payments Network (EPN). These ACH networksmay interact to settle ACH transactions involving a party that has arelationship with only NACHA's ACH network or only the EPN. Otherbanking networks, such as CIRRUS, NYCE, and PULSE may also be used.

As illustrated in FIG. 1 , banking network 145 can be communicablycoupled to one or more databases such as financial account database 150and member database 155. These databases can have a variety ofinformation that can be utilized by the transacting in advance systems.For example, financial account database 150 includes account informationfor members of a financial institution. Member database 155 storesinformation about members (or customers) of a membership organization(or financial institution). For example, member database 155 may storeinformation associated with member devices such as mobile device 120 orpersonal computer 125, should the member choose to register the device.Additionally, membership database 155 can include information such asemployer, total balance of all accounts held at the membershiporganization, credit ratings, home ownership information, annual salary,length of membership, purchase history, user-selectable preferences fortransactions such as banking, and/or other information. In someembodiments, these two databases can be integrated into one database. Acomputer system associated with a membership organization, a bank, acredit union, or other financial institution within banking network 145may be able to access these (and other) databases for accountinformation, customer information, and other stored information.

FIG. 2 is a block diagram illustrating components that can be includedin a transacting in advance system 200 in accordance with variousembodiments of the present invention. Components in the transacting inadvance system 200 may be installed on mobile device 120, personalcomputer 125, POS device 130, or a computing device at a financialorganization for example. According to the embodiments shown in FIG. 2 ,the transacting in advance system 200 can include memory 210, one ormore processors 220, device registration module 230; processing module240, location determination module 250, point of transaction module 260,information module 270, mapping module 275, unique identifier module280, point of transaction detection module 285, image receiving module290, and GUI generation module 295. Other embodiments of the presentdisclosure may include some, all, or none of these modules andcomponents along with other modules, applications, and/or components.Still yet, some embodiments may incorporate two or more of these modulesinto a single module and/or associate a portion of the functionality ofone or more of these modules with a different module.

Memory 210 can be any device, mechanism, or populated data structureused for storing information. In accordance with some embodiments of thepresent invention, memory 210 can encompass any type of, but is notlimited to, volatile memory, nonvolatile memory and dynamic memory. Forexample, memory 210 can be random access memory, memory storage devices,optical memory devices, magnetic media, floppy disks, magnetic tapes,hard drives, SIMMs, SDRAM, DIMMs, RDRAM, DDR RAM, SODIMMS, erasableprogrammable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), compact disks, DVDs, and/orthe like. In accordance with some embodiments, memory 210 may includeone or more disk drives, flash drives, one or more databases, one ormore tables, one or more files, local cache memories, processor cachememories, relational databases, flat databases, and/or the like. Inaddition, those of ordinary skill in the art will appreciate manyadditional devices and techniques for storing information which can beused as memory 210.

Memory 210 may be used to store instructions for running one or moreapplications or modules on processor(s) 220. For example, memory 210could be used in one or more embodiments to house all or some of theinstructions needed to execute the functionality of device registrationmodule 230; processing module 240, location determination module 250,point of transaction module 260, information module 270, mapping module275, unique identifier module 280, point of transaction detection module285, image receiving module 290, and GUI generation module 295.

Device registration module 230 is configured to register one or moredevices with a customer account. Registration may include providing aphone number, if the device is a smartphone, for example. Registeringmay include a process where the customer downloads an applicationprovided by the transacting organization onto the device, enabling thecustomer to transact in advance. The customer may choose to registerdevices associated with family members or friends with the customer'saccount. Registering other people's devices with the customer's accountmay assist in completing transactions such as transferring or receivingfunds to or from the other person, allowing another person to complete atransaction for the customer, and in other transactions. The registereddevices may include any computing device including, but not limited to amobile phone, smartphone, tablet computer, laptop computer, desktopcomputer, communication device associated with a vehicle, and the like.In some embodiments, device registration module 230 is configured tocollect identifying information related to the user device. Theidentifying information may include a device fingerprint, ip address,phone number, etc. The device registration module 230 may be configuredto associate the user device with the customer account using theidentifying information. The device may be registered with the customeraccount prior to receiving the request for the transaction or during atransaction.

Processing module 240 is configured to process any transaction that isreceived. Processing may include withdrawing funds for pendingtransactions, documenting an insurance claim, etc. Processing module 240may be configured to determine whether it will be necessary for thecustomer to go to a point of transaction such as a physical location ora network location to complete the transaction. Processing module 240may also be configured to receive images from image receiving module290, process the image, and extract information from the image.

Location determination module 250 is configured to determine a currentlocation of the customer or receive an indication of where the userwishes to complete the transaction. Location determination module 250may be configured to receive information from the processing moduleregarding whether a location needs to be determined. Locationdetermination module may use functionality on the customer's mobiledevice to determine the user's location. Alternatively, the customer mayprovide a location by keying in a zip code or an address. Sometimes thelocation for completion of the transaction may be different than thecustomer's current location. For example, if the customer wishes totransfer money for pick-up by another, the customer may key in or statethe recipient's location. In some embodiments, the customer may providea recipient's name and allow the location determination module 250 todetermine a location associated with the recipient. For example, if therecipient has a registered device or is otherwise associated with thecustomer's account, the location determination module 250 may use thisinformation to locate the recipient. The location determination modulemay use address information stored in the customer's mobile device tolocate the recipient.

Point of transaction module 260 is configured to determine possiblepoints of transaction in a prescribed radius of the determined locationfor transaction completion, as supplied by the location determinationmodule 250. For example, the customer's transaction may include thepurchase of a gift card. Point of transaction module 260 is configuredto determine the points of transactions that are capable of dispensinggift cards. Point of transaction module 260 may be further configured todetermine whether the points of transaction are in working order tocomplete the transaction. For example, point of transaction module 260may determine that a particular point of transaction in the prescribedradius is out of gift cards. Thus, this point of transaction would notbe included in the possible points of transaction. Point of transactionmodule 260 may additionally be configured to provide the possible pointsof transaction to information module 270.

Information module 270 is configured to receive the possible points oftransaction from point of transaction module 260, gather information,including preference information, historical information, and publiclyavailable information and to provide a recommendation of a subset of thepossible points of transaction based on the information. In someembodiments, information module 270 is configured to access account andmember information from financial account database 150 and memberdatabase 155, which may include customer preference data and pastbehavioral data. Customer preferences may include user-selectablepreferences or criteria that the customer has provided to the financialinstitution or other transacting entity prior to the transaction. Suchpreferences may include the customer's preferred type of point oftransaction location (e.g., kiosk, ATM, drive-through, POS device atcertain store, network location) for various transactions. Preferencesmay include a preference of a type of point of transaction or a specificpoint of transaction depending on the type of transaction being staged,a time the customer is staging the transaction, a specified completiontime of the transaction, the device used for staging, and the like. Forexample, suppose the customer has specified a preference for schedulingtransactions at a point of transaction in a grocery store when thetransaction is staged from the customer's at-home computer. If a requestis received from the customer's at-home computer, then the point oftransaction at a grocery store may be automatically selected, or atleast included in the list of recommended possible points oftransactions. Devices, such as the at-home computer may be identified bydevice fingerprinting, internet protocol address, or the like. In someembodiments, a request is received through a particular type of channeland/or in a particular manner, such as communication received from avehicle device, communication sent via email from a home computer,communication sent via mobile application on a user mobile device, etc.The customer may provide additional preferences or have particularhistory with one channel and/or manner or another, which may be used inrecommending points of transaction. Customer preferences also mayinclude a maximum wait time a customer is willing to wait at a point oftransaction or a maximum radius that the customer is willing to travelto a point of transaction from the identified location, or maximum feesthe customer is willing to pay for a transaction.

Past behavioral data may include any information regarding pasttransactions such as where the customer typically performs certain typesof transactions. For example, if a customer typically deposits checks atATMs in grocery stores, or consistently withdraws cash at abrick-and-mortar bank, the customer may be directed to a correspondinglocation for the type of transaction requested. Past behavior relatingto similar transactions may be used as well.

Additionally, public data may be accessed in determining andrecommending points of transactions or routes to the points oftransactions. For example, public data may be accessed to determine thesafety of a given point of transaction. Or, for example, if a customertraveling abroad requests a cash withdrawal, the points of transactioncapable of completing the transaction, within a given radius, may begiven a rank or ordered in a list according to crime rate associatedwith that area based on public records. Crime rates may be determinedfor each possible point of transaction, the crime rate in the localarea, and/or crime rate in a predefined area close to the point oftransaction. Additionally, public records may be used to determine thesafest route to get to a point of transaction. Public records orinformation supplied by an entity associated with the point oftransaction may indicate which points of transactions are out of service(or the functionality of each is out of service), which have long lines,or any other reason to avoid a point of transaction. Fees associatedwith the transaction at each point of transaction may be determined frominternal or external databases.

Each point of transaction may be given a score based on one or more ofthe various factors including the crime rate, past behavioral data, orcustomer preferences.

Mapping module 275 may be configured to provide a map of the recommendedpoints of transaction. The map may be user-customizable and may includedirections to the points of transaction.

Unique identifier module 280 is configured to generate a uniqueidentifier for the transaction. In some embodiments the uniqueidentifier is based at least in part on the selected point oftransaction. The unique identifier module 280 may be further configuredto populate the unique identifier with information relating to thetransaction. This unique identifier is communicated to the customer forpresentation at the point of transaction. The unique identifier mayinclude an account number, transaction identifier, type of transaction,date and time of when the transaction was staged, staging location,details of the device used, transaction amounts, recipients, window fortransaction completion, etc. Generally, for information securityreasons, it is preferable to include less information in the uniqueidentifier. However, various factors may dictate the amount ofinformation to be included. For example, the user may provide apreference of the amount and type of information to be included in theunique identifier. Or the relationship of the transacting entity and thepoint of transaction and/or the capabilities of the point of transactionmay determine the amount of information included in the uniqueidentifier. For example, if the point of transaction has an establishedrelationship (e.g., with an affiliated organization), and/or has signedagreements with the transacting entity, then less information may berequired in the unique identifier to complete the transaction. In afurther example, the unique identifier may include only a transactionidentifier (e.g., a number or alphanumeric code). Upon presentation ofthe transaction identifier, with the proper authorization andcapability, the point of transaction may directly access the userrecords using the transaction identifier and retrieve the transactiondetails to sufficiently complete the transaction without further actionby the transacting entity. In some embodiments, the unique identifierincludes or is a machine-readable identifier, such as a quick responsecode or a universal product code. In some embodiments, the uniqueidentifier contains sufficient information to complete the transactionwithout accessing the transacting entity's records. In some embodiments,additional information is required and the point of transaction uses theunique identifier to alert the transacting entity and requestinformation relating to the transaction. The transacting entity may thenuse the unique identifier, or other information, to access the userrecords to identify the transaction and communicate the informationrelating to the transaction to the point of transaction for transactioncompletion. In some embodiments, the unique identifier by itself or incombination with additional identifying information such as the userdevice is used to authenticate the customer at the point of transaction.The unique identifier may further include information relating theuser's preferences at the point of transaction. For example, the uniqueidentifier may indicate that the user does not prefer receipts, orprefers to receive a receipt showing balances of all accounts, etc. Insome embodiments, the transacting entity supplying the unique identifieris a membership organization and the unique identifier is a memberidentification number. In some embodiments, the unique identifier module280 is further configured to assign an expiration time to the uniqueidentifier such that if the unique identifier is not used within acertain period of time or by a certain date, the unique identifiercannot be used to complete the transaction. The customer may be requiredto re-submit the transaction or take some other action to revive thetransaction.

Point of transaction detection module 285 is configured to detect whenthe device is near a possible point of transaction, such as by using ageo-fencing functionality. Point of transaction detection module 285 maybe further configured to alert the customer that the customer is near apossible point of transaction after detecting that the device is near apossible point of transaction. The detected possible point oftransaction may be the selected point of transaction or it may be apoint of transaction that is different than the selected point oftransaction. If the detected point of transaction is the selected pointof transaction, the selected point of transaction may automaticallyprocess the transaction (if additional processing is necessary) suchthat the user need only authenticate his or her self at the selectedpoint of transaction. Point of transaction detection module 285 may befurther configured to communicate to the customer that the transactionis ready for completion. If the detected possible point of transactionis not the selected point of transaction, the point of transactiondetection module 285 may be configured to communicate to the customerthat the customer is near a possible point of transaction and that thetransaction can be completed at that point of transaction, if thecustomer chooses. The customer may indicate that the customer willcomplete the transaction at the new point of transaction. In someembodiments, a new unique identifier may be generated for the new pointof transaction and sent to the customer. If so, the original uniqueidentifier may be expired early or deactivated for security purposes.The user device may be detected to begin completion of the transactionusing various methods. For example, the user may keep an application onthe device in a continuous transmission mode, broadcasting its locationvia a mobile application to the transacting entity or points oftransaction. If so, when the user is within a predetermined radius ofthe transacting entity or point of transaction, the transaction may beprocessed such that the transaction is ready for completion when theuser arrives at the transacting entity or point of transaction. Inanother example, a user may open a mobile application and log on whenapproaching a transacting entity or point of transaction, thus startingthe transmission signaling the user's presence to the transacting entityor point of transaction.

Image receiving module 290 is configured to receive a digital image of acheck, insurance document, or other image for a transaction that hasbeen remotely captured by a user (e.g., using a camera or screen capturefunction on a mobile device). The digital image can be captured atdedicated terminals 110, an ATM in ATM network 115, mobile device 120,personal computer 125, vehicle 135, and/or point of sale (POS) device130. In some embodiments, image receiving module 290 can requestadditional images from the user (e.g., if the image cannot besuccessfully processed).

GUI generation module 295 can generate one or more user interfacescreens designed to receive user inputs, select accounts for deposit,display the maps from the mapping module 275, and/or process otherrequests from the customer.

FIG. 3 is a flow chart illustrating a set of example operations 300 fortransacting in advance in accordance with some embodiments of thepresent invention. The operations described with respect to FIG. 3 maybe accomplished by one or more of the components described with respectto FIG. 2 . Operations described with respect to FIGS. 4 and 5 may beincluded in FIG. 3 . FIG. 3 is described with respect to a bankingactivity. However, the operations described with respect to FIG. 3 canapply to various other types of transactions in other industries.

In operation 310, a financial institution receives a registrationrequest from a customer to register one or more devices with thefinancial institution by associating the device with the customer'saccount. As discussed, registration may include gatheringdevice-identifying information such as a phone number or devicefingerprint.

In operation 320, a request for a financial transaction is received froma customer using a registered device. The request may be made via awebsite (usaa.com), via a mobile application (mobile.usaa), or via atablet computer (USAA app for iPad). Using the registered device, thecustomer proceeds with the transaction. In some examples, at this point,the customer may be able to complete an entire transaction. However, inother examples, the customer has initiated and completed a portion ofthe transaction, but to finish the transaction, the customer or arepresentative must physically go to a banking location such as an ATMor POS device. For example, the transaction may include the customercashing a check. Using the customer's registered device, the customermay send an image of the check to the financial institution. Thefinancial institution can process the transaction. However, to receivecash from the check, the customer, or a representative, must physicallygo to a banking location.

Operations 330-360 illustrate the steps of determining and recommendingbanking locations to the customer to complete the transaction. Inoperation 330, location information associated with the transactioncompletion location is determined and identified. In some embodiments,the customer wants to complete the transaction at a banking locationclose or within a certain proximity to the customer's current location.The customer's current location is determined using any method known inthe art. For example, the customer's device may be capable ofdetermining the customer's location, which may be communicated to thefinancial institution via an application. Or the customer may provide acurrent location to the application. The customer may select a locationfrom a map that is presented to the customer. In other embodiments, thecustomer may want to complete the transaction at a location other thanthe customer's current location. The customer may indicate a generalarea, such as a zip code, or a particular area, such as an address,where the customer would like to complete the transaction. For example,if a third party not in the vicinity of the customer is the recipient ofthe transaction or will be completing the transaction (i.e. picking upthe cash), the customer may provide an address of the third party.Alternatively, an application could retrieve and tag locationinformation from the customer's calendar. Ultimately, the locationinformation regarding where the customer chooses to complete thetransaction is used to identify banking locations capable of completingthe transaction that are within a user-defined or predefined radius ofthe identified location. A list of the identified banking locations maybe compiled.

In operation 340, customer preferences, past behavioral data, andpublicly available data may be accessed to order and tailor the list ofbanking locations capable of completing the transaction.

In operation 350, the customer is provided with a recommendation ofbanking locations where the customer may complete the transaction. Therecommendation can be based on the information accessed in thedatabases, including the preexisting preferences, public data, and pastbehavioral data. The recommendation may include a list of bankinglocations, including a description of the banking locations, and drivingdirections, maps, fees associated (if any), safety information, andcurrent wait times based upon pending transactions from customers usinga similar technology for each listed banking location.

In operation 360, the customer selects the banking location andcommunicates the selection to the financial institution. Next, inoperation 370, the financial institution processes the selection andschedules the transaction for the selected banking location. Schedulingthe transaction may include placing the transaction in a queue, to becompleted at a particular time or to be completed at the customer'sconvenience after providing proper identification to the bankinglocation. Additional information is provided to the selected bankinglocation as necessary. A confirmation message including details aboutthe scheduled transaction and the selected banking location may be sentto the customer. A unique identifier may be sent to the customer thatcan be used to provide transaction details to the selected bankinglocation and/or authentication purposes.

In operation 380, the customer is authenticated when the customerreaches the banking location. Either or both the banking location andthe financial institution may authenticate the customer at the bankinglocation. In some embodiments the banking location is affiliated withthe financial institution. The customer may be authenticated by anymethod known in art, including by supplying an identification card, apin number associated with a card, information, biometric data,information regarding the registered device, and so on. In someembodiments, for security purposes, several identifying pieces ofinformation may be used in combination to authenticate the user and toidentify the transactions. If the customer received a confirmation emailor other communication that included a unique identifier as discussedabove, the unique identifier may be used to identify the transactionand/or authenticate the user. The unique identifier may include a quickresponse code or universal product code that the customer presents tothe banking location to authenticate the customer. In a non-limitingexample, the user may be asked or required to present the uniqueidentifier only on a device registered with the customer account, andthe user may also be required to provide biometric evidence identifyingthe user (e.g., voice, fingerprint, real-time photograph or video).After authentication, the customer can interact with the bankinglocation to complete the scheduled transaction, as indicated inoperation 390. In some embodiments the QR code or a transactionidentifier is all that is required for the user to complete thetransaction.

FIG. 4 is a flow chart illustrating a set of example operations 400 fortransacting in advance in accordance with some embodiments of thepresent invention. The operations described with respect to FIG. 3 maybe accomplished by one or more of the components described with respectto FIG. 2 . Operations described with respect to FIGS. 4 and 5 may beincluded in FIG. 4 .

Receiving operation 410 receives a request for a transaction. Therequest may be received from a registered user device. In processingoperation 420, the request is processed. During the processing operation420, it is determined that user interaction at a point of transaction isnecessary to complete the transaction.

Determining possible points of transaction operation 430 determinespossible points of transaction. The possible points of transaction arebased on a location of the user (or a location the user indicates thetransaction should be completed) and a type of the requestedtransaction. For example, a possible point of transaction may be a pointof transaction within a predetermined radius of the user with thecapability to complete the transaction. The possible points oftransaction may be determined by a relationship of the point oftransaction with the transacting entity, and/or capability.

Accessing operation 440 accesses the user's preferences and/or otherinformation. Such information may include maximum wait times preferred,a type of point of transaction, a point of transaction coordinating witha scheduled location on the user's calendar, points of transaction whereprevious similar transactions took place, points of transaction usedbefore or during a certain time of day, lighting or other safetyinformation relating to the points of transaction, etc. Informationrelated to registered devices may be accessed. In some embodiments, thecustomer provides a user preference list identifying the preferredcharacteristics of the points of transactions.

Recommending operation 450 recommends a subset of possible points oftransaction. The recommendation may be based on the information accessedin accessing operation 440. For example, the request may be receivedfrom a registered device of the customer. It may be determined that theuser prefers a certain type of point of transaction while using theregistered device. This information may be used in combination withother information to determine options of points of transactions thatwould be most helpful to the customer.

Receiving point of transaction operation 460 receives a selection of apoint of transaction from the user. Based on this point of transaction,the transaction may be put into a queue for the user so that the userneed only provide identification to the point of transaction to completethe transaction. In some embodiments a unique identifier is provided tothe user which may serve as the user's identification.

FIG. 5 is a flow chart illustrating a set of example operations 500 fortransacting in advance in accordance with some embodiments of thepresent invention. The operations described with respect to FIG. 5 maybe accomplished by one or more of the components described with respectto FIG. 2 . Operations described with respect to FIGS. 3 and 4 may beincluded in FIG. 5 .

Receiving operation 510 receives a request for a transaction. Thetransaction must be completed at a point of transaction. The point oftransaction may be a website or it may be a physical location such as anATM.

Identifying operation 520 identifies a general location for completionof the transaction. The location may be provided by the user such as byuser input. Or the location may be determined by user selection ofcommon locations or selection of a recipient to complete thetransaction, etc. For example, if a customer selects a recipient, alocation near the recipient may be provided or determined based on therecipient's registered device or past transactions with the recipient.

Determining possible points of transaction operation 530 determinespossible points of transaction within a predetermined distance of theidentified location. The predetermined distance may be a user-selectableitem or it may be determined by the availability of points oftransaction in and around the identified location.

Displaying possible points of transaction operation 540 displays thepossible points of transaction. The possible points of transaction maybe displayed on a user-customizable map, or the possible points oftransaction may be provided in a selectable list.

Receiving point of transaction operation 550 receives a selection of apoint of transaction from the user.

Unique identifier generating operation 560 generates a unique identifierfor the transaction. The unique identifier may be based on the selectedpoint of transaction, providing additional information if needed tocomplete the transaction. The unique identifier may include informationrelating to the transaction such as account numbers, amount information,order information, etc. The unique identifier may be simply a number, orit may be a quick response code or universal product code.

Providing unique identifier operation 570 provides the unique identifierto the user. The unique identifier may be communicated via email, textmessage, user account on a website, or through a phone call from arepresentative. In some embodiments, the content of the uniqueidentifier is based on the mode of communication. The unique identifiermay be presented to the point of transaction to complete thetransaction.

FIGS. 6-21 are examples of user interfaces that may be used in variousembodiments. For example, the illustration in FIG. 6 is an example menufor the customer to indicate various options with a mobile application,including an option to transfer or deposit funds. Should the user decideto transfer or deposit funds (605), the user may be required to log onas depicted in FIG. 7 . FIG. 7 depicts alternative methods of loggingon, shown on two alternative user interfaces, one requiring an online idand password (705), and the other simply requiring a PIN (710). FIG. 8depicts an example user interface displayed when the user selects thetransfer/deposit funds option on the menu. FIG. 9 depicts an exampleuser interface displayed if the user selects deposit funds option. Forexample, the user may select “Retail Location Deposit” or“Deposit@Mobile.” FIG. 10 depicts a user interface allowing the user toselect a deposit account, or enter a cash amount (1005). FIG. 10 alsodepicts a user interface allowing the user to select an account (1010).FIG. 11 depicts a user interface with a selection of a particulardeposit account (1105). FIG. 11 also depicts a user interface displayinginformation pertinent to the transaction and notifying the user that theinformation will be sent to a retail system (1110). FIG. 12 depicts auser interface displaying a map in which a unique identifier (ReferenceNumber) can be used to complete the transaction. FIG. 13 depicts a userinterface listing all pending transactions for the user (1305). FIG. 13also depicts a user interface showing additional details related to aparticular pending transaction (1310). The more specific informationdisplayed in 1310 appears when the user selects the particular pendingtransaction.

FIG. 14 depicts an example user interface for using “Advance Deposit.”FIG. 15 depicts a user interface or request for a transaction to send ordeposit a user-supplied amount of money. The user may select whether theuser is depositing the funds using cash or a check. FIG. 16 depicts auser interface displaying a map depicting several possible points oftransaction locations. In some embodiments the points of transaction areuser-selectable on the map. FIG. 17 depicts a user interface allowing auser to input an address, specifying the selected point of transaction.FIG. 18 depicts a user interface showing the selected or identifiedpoint of transaction. The user interface allows the user to select a newaddress as well. FIG. 19 depicts a user interface communicating to theuser that the location for the point of transaction is set. FIG. 20depicts a user interface displaying the destination information, whichis an account in the example, and the transaction location whichincludes the name and address of the retail location. FIG. 21 depicts auser interface displaying example of a Quick Response code and atransaction identifier, which together or separately may be a uniqueidentifier. The Quick Response code and/or the transaction identifiermay be sent to the user.

In some examples, the transacting in advance system may be used tofacilitate a transaction between two different people. In someembodiments, the other person has a registered device associated withthe customer's account. This enables another person to use a registereddevice in a similar manner as the customer, employing the sametechniques and methods described above. If, for example, the otherperson is the recipient of a transaction, after the transaction isrequested by the customer, the recipient may use her registered deviceto locate a banking location and complete the staged transaction. Forexample, if a parent wants to send his or her child, a college studentliving in a different state, some cash to pay for a cab ride home, theparent can schedule a transaction to be completed at a banking locationclose to the child. The banking location may be selected by the parentor the child using one of the registered devices and the techniquesdescribed above. At the selected banking location, the child willprovide identification or authentication. The registered device mayauthenticate the child in some examples. In some examples, the parent orthe financial institution may send a code or pin to the child's mobiledevice or email address. The child may be required to produce the codeor pin in order to receive the cash from the banking location. Or, insome embodiments, the financial institution may provide a video orphotograph of the person at the banking location to enable the parent toverify that the person at the banking location is in fact the intendedbeneficiary. The video or photograph may be sent to the parent's mobiledevice for verification. Alternatively, the financial institution mayprovide internal verification by comparing the photo or video withstored data. The parents may include additional instructions to thefinancial institution to verify the child's identity, such as requiringa driver's license. In some embodiments, the financial institution orthe parent may temporarily take over the recipient's mobile device andprovide the information necessary to complete the transaction. Aconfirmation of the transaction may be sent to both registered devices.

If the recipient's device is not pre-authorized or registered, therecipient may provide other identification verification. For example,the recipient may have provided the financial institution identificationsuch as DNA, fingerprint, or a photograph in the past, or can offer suchevidence contemporaneously with the transaction.

In an embodiment, fees of the identified banking locations may beassessed and the information may be provided to the customer and to athird party of a transaction, if applicable. In some examples, the feesmay be collected from the person initiating the transaction. In someembodiments, the financial institution reimburses the person, if theperson is a customer.

To enhance the security of the information passed between customers andthe banking location, in some embodiments, there may be an encrypted RFfield around the point of transaction. In an embodiment, directconnections between a customer's mobile device and the point oftransaction are secured. Alternatively, the communication path betweenthe customer's mobile device and the financial institution's back endsystem at the banking location is encrypted.

In some embodiments, a transaction is staged such that a vendor orrepresentative of the transacting entity receives or is notified of thetransaction. A mobile unit associated with the transacting entity willbe notified and will go to a specified location such as the customer'shome or office to complete the transaction.

Some non-limiting examples of how customers may use various embodimentsof the present invention are described in the following scenarios.

A customer may be waiting in line at an ATM or other point oftransaction. While waiting in line at an ATM, the customer stages his orher transaction so that as soon as the ATM becomes available, thecustomer need only be authenticated for the transaction to be completed.In some embodiments, the customer's mobile device alerts the customerthat the customer is near the ATM and asks the customer if he or shewould like to complete the transaction.

In a non-limiting example, a customer initiates a transaction whilewaiting in the drive-up teller window line at the bank. The transactionis processed and ready for completion prior to the customer reaching theteller.

In a non-limiting example, a parent provides cash to a child bytransferring money for the child to pick up at a banking location nearthe child. Or a retailer may schedule a cash money order to be picked upor delivered at an ATM or other point of transaction.

In another non-limiting example, a customer syncs a calendar to supplyinformation such as location and time for scheduled transactions (e.g.,dinner reservations noted in the calendar are scheduled at a certaintime and the customer wants to withdraw money from an ATM close to therestaurant; the ATM will be prepared to complete the transaction closeto scheduled dinner time).

In another non-limiting example, a person applies for life insurance andcompletes the application process except the finishing step of providingauthentication, which is scheduled to be completed around lunchtime at apoint of transaction near the person's office building.

In another non-limiting example, a customer stages a cash withdrawal andis guided to ATMs or banking locations with the lowest fees.

In another non-limiting example, a person traveling abroad requests atransaction and is provided several banking locations with routes to thebanking locations, in accordance with the person's preference of bankinglocations within walking distance.

In another non-limiting example, a customer stages his transaction whilewaiting in line at the ATM. The customer may receive marketing materialsand offers based on the customer's financial needs while waiting inline.

Exemplary Computer System Overview

Embodiments of the present invention include various steps andoperations, which have been described above. A variety of these stepsand operations may be performed by hardware components or may beembodied in machine-executable instructions, which may be used to causea general-purpose or special-purpose processor programmed with theinstructions to perform the steps. Alternatively, the steps may beperformed by a combination of hardware, software, and/or firmware. Assuch, FIG. 22 is an example of a computer system 2200 with whichembodiments of the present invention may be utilized. According to thepresent example, the computer system includes a bus 2205, at least oneprocessor 2210, at least one communication port 2215, a main memory2220, a removable storage media 2225, a read only memory 2230, and amass storage device 2235.

Processor(s) 2210 can be any known processor, such as, but not limitedto, an Intel® Itanium® or Itanium 2® processor(s), or AMD® Opteron® orAthlon MP® processor(s), or Motorola® lines of processors. Communicationport(s) 2215 can be any of an RS-232 port for use with a modem baseddialup connection, a 10/100 Ethernet port, or a Gigabit port usingcopper or fiber. Communication port(s) 2215 may be chosen depending on anetwork such a Local Area Network (LAN), Wide Area Network (WAN), or anynetwork to which the computer system 2200 connects.

Main memory 2220 can be Random Access Memory (RAM), or any other dynamicstorage device(s) commonly known in the art. Read only memory 2230 canbe any static storage device(s) such as Programmable Read Only Memory(PROM) chips for storing static information such as instructions forprocessor 2210.

Mass storage 2235 can be used to store information and instructions. Forexample, hard disks such as the Adaptec® family of SCSI drives, anoptical disc, an array of disks such as RAID, such as the Adaptec familyof RAID drives, or any other mass storage devices may be used.

Bus 2205 communicatively couples processor(s) 2210 with the othermemory, storage and communication blocks. Bus 2205 can be a PCI/PCI-X orSCSI based system bus depending on the storage devices used.

Removable storage media 2225 can be any kind of external hard-drives,floppy drives, IOMEGA® Zip Drives, Compact Disc-Read Only Memory(CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disk-Read OnlyMemory (DVD-ROM).

The components described above are meant to exemplify some types ofpossibilities. In no way should the aforementioned examples limit thescope of the invention, as they are only exemplary embodiments.

Terminology

Brief definitions of terms, abbreviations, and phrases used throughoutthis application are given below.

The terms “connected” or “coupled” and related terms are used in anoperational sense and are not necessarily limited to a direct physicalconnection or coupling. Thus, for example, two devices may be coupleddirectly, or via one or more intermediary media or devices. As anotherexample, devices may be coupled in such a way that information can bepassed therebetween, while not sharing any physical connection with oneanother. Based on the disclosure provided herein, one of ordinary skillin the art will appreciate a variety of ways in which connection orcoupling exists in accordance with the aforementioned definition.

The phrases “in some embodiments,” “according to some embodiments,” “inthe embodiments shown,” “in other embodiments,” and the like generallymean the particular feature, structure, or characteristic following thephrase is included in at least one embodiment of the present invention,and may be included in more than one embodiment of the presentinvention. In addition, such phrases do not necessarily refer to thesame embodiments or different embodiments.

If the specification states a component or feature “may”, “can”,“could”, or “might” be included or have a characteristic, thatparticular component or feature is not required to be included or havethe characteristic.

The term “responsive” includes completely or partially responsive.

The term “module” refers broadly to a software, hardware, or firmware(or any combination thereof) component. Modules are typically functionalcomponents that can generate useful data or other output using specifiedinput(s). A module may or may not be self-contained. An applicationprogram (also called an “application”) may include one or more modules,or a module can include one or more application programs.

The term “network” generally refers to a group of interconnected devicescapable of exchanging information. A network may be as few as severalpersonal computers on a Local Area Network (LAN) or as large as theInternet, a worldwide network of computers. As used herein “network” isintended to encompass any network capable of transmitting informationfrom one entity to another. In some cases, a network may be comprised ofmultiple networks, even multiple heterogeneous networks, such as one ormore border networks, voice networks, broadband networks, financialnetworks, service provider networks, Internet Service Provider (ISP)networks, and/or Public Switched Telephone Networks (PSTNs),interconnected via gateways operable to facilitate communicationsbetween and among the various networks.

Embodiments of the present invention may be provided as a computerprogram product which may include a machine-readable medium havingstored thereon instructions which may be used to program a computer (orother electronic devices) to perform a process. The machine-readablemedium may include, but is not limited to, floppy diskettes, opticaldisks, compact disc read-only memories (CD-ROMs), and magneto-opticaldisks, ROMs, random access memories (RAMs), erasable programmableread-only memories (EPROMs), electrically erasable programmableread-only memories (EEPROMs), magnetic or optical cards, flash memory,or other type of media/machine-readable medium suitable for storingelectronic instructions. Moreover, embodiments of the present inventionmay also be downloaded as a computer program product, wherein theprogram may be transferred from a remote computer to a requestingcomputer by way of data signals embodied in a carrier wave or otherpropagation medium via a communication link (e.g., a modem or networkconnection).

While, for convenience, embodiments of the present invention aredescribed with reference to staging transactions, embodiments of thepresent invention are equally applicable to other types of transactions.For example, various embodiments of the present invention contemplatescheduling orders and/or prepaying while at a drive through restaurant,pharmacy, etc.

Also, for the sake of illustration, various embodiments of the presentinvention have herein been described in the context of computerprograms, physical components, and logical interactions within moderncomputer networks. Importantly, while these embodiments describe variousaspects of the invention in relation to modern computer networks andprograms, the method and apparatus described herein are equallyapplicable to other systems, devices, and networks as one skilled in theart will appreciate. As such, the illustrated applications of theembodiments of the present invention are not meant to be limiting, butinstead exemplary. Other systems, devices, and networks to whichembodiments of the present invention are applicable include, but are notlimited to, other types of communication and computer devices andsystems. More specifically, embodiments are applicable to communicationsystems, services, and devices such as cell phone networks andcompatible devices. In addition, embodiments are applicable to alllevels of computing from the personal computer to large networkmainframes and servers.

In conclusion, embodiments of the present invention provide novelsystems, methods and arrangements for systems and methods to stagetransactions. While detailed descriptions of one or more embodiments ofthe invention have been given above, various alternatives,modifications, and equivalents will be apparent to those skilled in theart without varying from the spirit of the invention. For example, whilethe embodiments described above refer to particular features, the scopeof this invention also includes embodiments having differentcombinations of features and embodiments that do not include all of thedescribed features. Accordingly, the scope of the present invention isintended to embrace all such alternatives, modifications, and variationsthat fall within the scope of the claims, together with all equivalentsthereof. Therefore, the above description should not be taken aslimiting the scope of the invention, which is defined by the appendedclaims.

What is claimed is:
 1. A method comprising: receiving a request for atransaction, wherein completion of the transaction requires userinteraction at a point of transaction; identifying, by a processor, alocation in relation to the transaction; determining, by the processor,possible points of transaction within a specified distance of theidentified location; causing a display of the possible points oftransaction; receiving a selection of one of the possible points oftransaction; generating, by the processor, a first machine-readableunique identifier for the transaction based on the selected point oftransaction; and providing the first machine-readable unique identifierfor use at the selected point of transaction, wherein the firstmachine-readable unique identifier is used to complete the transaction.2. The method of claim 1, wherein providing the first machine-readableunique identifier comprises populating the first machine-readable uniqueidentifier with information relating to the transaction.
 3. The methodof claim 2, wherein a content of the information relating to thetransaction is based at least in part on a relationship with theselected point of transaction.
 4. The method of claim 2, wherein acontent of the information relating to the transaction is based at leastin part on a capability of the selected point of transaction.
 5. Themethod of claim 2, wherein the information relating to the transactioncomprises an account number, a type of transaction, and a transactionidentifier.
 6. The method of claim 1, wherein the first machine-readableunique identifier is a transaction identifier.
 7. The method of claim 1,wherein the first machine-readable unique identifier includes userpreferences.
 8. The method of claim 1, wherein the firstmachine-readable unique identifier is either a quick response code or auniversal product code.
 9. The method of claim 1, wherein the selectedpoint of transaction is associated with an affiliated organization, andwherein information relating to the transaction is accessed by theselected point of transaction using the first machine-readable uniqueidentifier.
 10. The method of claim 1, the method further comprising:receiving the first machine-readable unique identifier; accessing userrecords to identify the transaction; and communicating, to the selectedpoint of transaction, information relating to the transaction, whereinthe information relating to the transaction is to complete thetransaction at the selected point of transaction.
 11. The method ofclaim 1, wherein identifying, by the processor, the location for thecompletion of the transaction comprises detecting a location of the userdevice.
 12. The method of claim 1, the method further comprising:authenticating a user at the selected point of transaction using thefirst machine-readable unique identifier.
 13. The method of claim 1,wherein providing the first machine-readable unique identifier comprisesassigning an expiration time to the first machine-readable uniqueidentifier.
 14. The method of claim 1, the method further comprising:detecting that a user is within a radius of the selected point oftransaction; scheduling the completion of the transaction at theselected point of transaction; and communicating to the user that thetransaction is ready for the completion.
 15. The method of claim 1, themethod further comprising: detecting that a user is within a radius ofone of the possible points of transaction that is not the selected pointof transaction; and communicating to the user that the transaction canbe completed at the one of the possible points of transaction that isnot the selected point of transaction.
 16. The method of claim 1, themethod further comprising: registering a user device with a customeraccount, wherein registering the user device with the customer accountcomprises: receiving a request to register the user device with thecustomer account; collecting identifying information related to the userdevice; and associating the user device and the identifying informationrelated to the user device with the customer account.
 17. The method ofclaim 1, wherein the possible points of transaction are physicallocations, and wherein displaying the possible points of transactioncomprises indicating the possible points of transaction on a map.
 18. Anon-transitory machine-readable medium having machine-executableinstructions stored thereon that, when executed by one or moreprocessors, direct the one or more processors to perform a methodcomprising: receiving a request for a transaction, wherein completion ofthe transaction requires user interaction at a point of transaction;identifying a location in relation to the transaction; determiningpossible points of transaction within a specified distance of theidentified location; causing a display of the possible points oftransaction; receiving a selection of one of the possible points oftransaction; generating a first machine-readable unique identifier forthe transaction based on the selected point of transaction, providingthe first machine-readable unique identifier for use at the selectedpoint of transaction, wherein the first machine-readable uniqueidentifier is used to complete the transaction.
 19. A system comprising:one or more processors; and computer-readable code that programs the oneor more processors to: receive a request for a transaction, whereincompletion of the transaction requires user interaction at a point oftransaction; identify a location in relation to the transaction;determine possible points of transaction within a specified distance ofthe identified location; cause the possible points of transaction to bedisplayed on a user interface of the user device; receive a selection ofone of the possible points of transaction; generating a firstmachine-readable unique identifier for the transaction based on theselected point of transaction, providing the first machine-readableunique identifier for use at the selected point of transaction; receivethe first machine-readable unique identifier from the selected point oftransaction; access user records to identify the transaction;communicate the information relating to the transaction to the selectedpoint of transaction, wherein the communicated information relating tothe transaction is to complete the transaction at the selected point oftransaction; and complete the transaction.
 20. The system of claim 19,wherein the location in relation to the transaction is identified bydetecting a location of a user device.